Skip to content

feat: support deploying aleph-vm from a Git branch#10

Merged
odesenfans merged 2 commits intomainfrom
feat/deploy-vm-from-branch
Apr 23, 2026
Merged

feat: support deploying aleph-vm from a Git branch#10
odesenfans merged 2 commits intomainfrom
feat/deploy-vm-from-branch

Conversation

@odesenfans
Copy link
Copy Markdown
Contributor

Summary

  • Add support for deploying aleph-vm from a CI-built .deb artifact (GitHub Actions) instead of a GitHub release
  • New fetch_vm_deb_from_branch() function uses gh run list + gh run download to fetch the .deb locally, then scps it to each CRN
  • Configurable via manifesto.yml (branch field) or ALEPH_VM_BRANCH env var; falls back to existing release-based flow when unset

Usage

# manifesto.yml
aleph-vm:
  branch: "my-feature-branch"

or:

ALEPH_VM_BRANCH=my-feature-branch ./scripts/crn-up.sh --install

Test plan

  • Deploy a testnet with ALEPH_VM_BRANCH=main and verify the .deb is fetched from CI and installed
  • Deploy a testnet with the default version field and verify existing release-based flow still works
  • Verify error message when branch has no successful CI run

Add the ability to deploy aleph-vm from a CI-built .deb artifact instead
of a GitHub release. This uses the gh CLI to download the artifact from
the latest successful workflow run for the specified branch.

Configurable via manifesto.yml (branch field) or the ALEPH_VM_BRANCH
environment variable. Falls back to the existing release-based flow when
no branch is set.
@odesenfans odesenfans merged commit ef50b29 into main Apr 23, 2026
1 check passed
@odesenfans odesenfans deleted the feat/deploy-vm-from-branch branch April 23, 2026 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant